Skip to main content

acc log

Create a new work log entry with message, tags, and project association.

Usage

acc log [OPTIONS]

Options

FlagDescription
-m, --message <TEXT>Entry content (can be used multiple times for multi-line entries)
-t, --tags <TAGS>Comma-separated tags (e.g., backend,api,bugfix)
-p, --project <PROJECT>Associate with a specific project by 3-letter identifier
--editOpen your default editor to write the entry

Examples

Basic Entry

acc log -m "Fixed authentication bug in login flow"

Multi-line Entry

acc log -m "Implemented new user dashboard:" \
-m "- Added activity timeline" \
-m "- Integrated notification center" \
-m "- Improved responsive design"

With Tags

acc log -m "Optimized database queries" -t backend,performance,database

With Project

acc log -m "Updated API documentation" -p API

Using Editor

acc log --edit

Opens your default editor (set via $EDITOR environment variable) with a template.

Combined Options

acc log -m "Deployed v2.1.0 to production" \
-t deployment,release,production \
-p WEB

Project Context

The CLI automatically determines which project to use:

  1. Explicit -p flag: Always takes precedence
  2. Local .accomplish.toml: Uses default_project if configured
  3. Directory mapping: Set up via acc init
  4. No default: Entry created without project association

Tag Best Practices

Use consistent tagging for better organization:

# Feature development
acc log -m "Added user profiles" -t feature,frontend,users

# Bug fixes
acc log -m "Fixed payment processing" -t bugfix,backend,payments

# Maintenance
acc log -m "Updated dependencies" -t maintenance,security

# Meetings and planning
acc log -m "Sprint planning meeting" -t meeting,planning

URL Detection

The CLI automatically converts bare URLs to markdown links:

acc log -m "Deployed to https://staging.myapp.com"
# Becomes: "Deployed to [https://staging.myapp.com](https://staging.myapp.com)"

Editor Integration

Set your preferred editor:

export EDITOR="code"    # VS Code
export EDITOR="vim" # Vim
export EDITOR="nano" # Nano

When using --edit, the CLI opens your editor with a template:

# Work Log Entry
# Lines starting with # are comments and will be ignored

Your work entry content goes here...

# Tags: backend,api,bugfix (comma-separated)
# Project: ABC (3-letter identifier, optional)

Requirements

  • Must be authenticated (acc login)
  • At least one of -m or --edit is required

Notes

  • Entries are timestamped automatically
  • URLs in messages are automatically converted to markdown links
  • Empty messages (after editing) are discarded
  • Tags are case-insensitive and normalized